Detection of artifacts resulting from image signal decompression

ABSTRACT

A method includes making a first determination as to whether a current pixel has a value which reflects a mosquito noise artifact, and determining whether to apply a filtering process at the current pixel based on a result of the first determination. In addition, or alternatively, a method includes making a second determination as to whether a current pixel has a value which reflects a ringing artifact, and determining whether to apply a filtering process at the current pixel based on a result of the second determination.

BACKGROUND

It is often desirable to apply compression-encoding to video signals prior to transmission or storage of the video signals. In some commonly employed compression-encoding strategies (e.g., ITU H.261/H.263/H.264 or MPEG 1/MPEG 2/MPEG 4), block transforms (e.g., discrete cosine transform, or “DCT”) are applied with motion compensation, followed by quantization of the transform coefficients and entropy encoding. Some of the video signal information is typically lost during compression encoding, particularly during the quantization stage. The loss of information may lead to reduced image quality upon de-compression of the video signal. It is desirable to employ certain approaches to counteract image artifacts generated upon de-compression.

One type of de-compression artifact is known as “mosquito noise”, which results from the abrupt truncation of high frequency DCT coefficients during quantization. Mosquito noise typically takes the form of small distortions (seen as “busyness”) near edges, especially edges of moving objects. It has proposed to mitigate mosquito noise by applying low pass filtering to the video signal after de-compression. However, the low pass filtering may introduce blurring throughout the image.

Another type of de-compression artifact is known as “ringing noise”. This too results from truncation of high frequency DCT coefficients and has the appearance of ripples that extend outwardly from edges. Again low pass filtering may be employed to mitigate ringing noise, but often at the cost of blurring the entire image.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a block diagram of an apparatus which generates a video display from a video bitstream in accordance with some embodiments.

FIG. 2 is a functional block diagram that illustrates some operations of a noise reduction block that is part of the apparatus of FIG. 1.

FIG. 3 is a flow chart that illustrates a mosquito noise detection process performed by the noise reduction block.

FIGS. 4 and 5 schematically illustrate aspects of the process of FIG. 3.

FIG. 6 is a functional block diagram that illustrates some operations of the noise reduction block in some embodiments.

FIG. 7 is a flow chart that illustrates a ringing noise detection process that may be performed in the noise reduction block either in addition to or instead of the mosquito noise detection process of FIG. 3.

DETAILED DESCRIPTION

FIG. 1 is a block diagram of an apparatus 100 which generates a video display from a video bitstream in accordance with some embodiments.

The apparatus 100 includes a source 102 of a video signal bitstream. For example, the video signal source 102 may receive a video signal via a communication channel (which is not separately shown) or may reproduce a video signal from a storage medium such as a DVD or a hard disk drive. For example, the video signal source may include a video tuner, a satellite earth station, or a DVD player. It will be assumed that the video signal bitstream represents a video signal that has been compression encoded, e.g., in accordance with one of the compression standards referred to above. The video signal source 102 may operate in accordance with conventional practices.

The apparatus 100 also includes a video decoder 104 which is coupled to the video signal source to de-compress the video signal bitstream supplied by the video signal source 102. The video decoder 104 may operate in accordance with conventional principles, and may tend to produce artifacts in the output video image, subject to amelioration via embodiments to be described below.

The apparatus 100 further includes a post-processing block 106 which is coupled to the video decoder 104. The post-processing block 106 performs one or more kinds of post processing on the decompressed video signal output from the video decoder 104. For example, the post-processing block 106 may perform one or more different kinds of noise reduction processing as in one or more of the embodiments described below.

In addition, the apparatus 100 includes a display device 108, such as a conventional television set or a computer display monitor. The display device 108 displays the video signal that is output from the post-processing block 106.

FIG. 2 is a functional block diagram that illustrates aspects of a noise reduction process performed in the post-processing block 106 in accordance with some embodiments. Block 202 represents the post-processing block (or a noise reduction sub-block) receiving an input video signal (e.g., directly or indirectly from the video decoder 104) that is to be subjected to noise reduction processing. Block 204 represents a process provided in accordance with some embodiments to detect locations (e.g., specific pixels), in the video signal received at 202, which exhibit mosquito noise artifacts. Block 206 represents a process in which filtering is applied to the input video signal received at 202 (based on results obtained by the mosquito noise detector 204), to mitigate the mosquito noise artifacts.

FIG. 3 is a flow chart that illustrates a mosquito noise detection process performed by the mosquito noise detector sub-block of the pre-processing/noise reduction block 106 in accordance with some embodiments. Block 302 in FIG. 3 represents receipt by the mosquito noise detector sub-block 204 of the decompressed video signal to be filtered for purposes of mosquito noise reduction.

In general, according to some embodiments, the mosquito noise detection process of FIG. 3 is at least partly a pixel-block-based process. In accordance with some embodiments, the same 8 pixel by 8 pixel blocks are used as in some conventional DCT compression encoding/decoding processes. 10×10 pixel blocks may alternatively be employed, as may blocks of other dimensions.

Block 304 represents pre-filtering that may be applied to the input video signal before performing edge detection processing. The pre-filtering is not required but may improve the accuracy of the subsequent edge detection.

As part of the pre-filtering, a 3×3 weighting matrix may be applied to a 3 pixel by 3 pixel array (neighborhood) NH9(x₀) centered at the currently processed pixel x₀ to implement a weighting function w. In some embodiments, the weighting matrix employed may be:

$\left\lbrack \left. \quad\begin{matrix} 1 & 2 & 1 \\ 2 & 4 & 2 \\ 1 & 2 & 1 \end{matrix} \right\rbrack \right.$

To reduce the complexity of the calculations, this two-dimensional matrix may be decomposed into two one dimensional matrices:

$\begin{bmatrix} 1 \\ 2 \\ 1 \end{bmatrix}*\begin{bmatrix} 1 & 2 & 1 \end{bmatrix}$

In some embodiments, the output of the pre-filter for the target pixel x₀ may be calculated as follows:

${\left( {1/16} \right)*\left( {\left( {\sum\limits_{x \in {{NH}\; 9{(x_{o})}}}{{w(x)}*\left\{ x \right\}}} \right) + 8} \right)},$

where w(x) is the value of the weighting matrix at the position of the pixel xεNH9(x₀), and {x} is the value of that pixel. It will be noted that 16 is the summation over the weighting matrix and 8 is one-half of that summation, the latter term being applied for purposes of rounding.

Edge detection processing as indicated at 306 follows the pre-filtering at 304. With the edge detection processing, an edge metric value EM(x₀) is calculated for each pixel, x₀ again designating the target pixel. Based on the edge metric values, blocks that are likely to exhibit mosquito noise artifacts are identified. These blocks may be edge blocks (blocks which include an edge) and blocks that are neighbors to blocks having strong edges.

Any one of a number of edge detectors may be employed. In some embodiments, the so-called Sobel edge detector may be employed, using the following matrices:

${E\_ h} = \begin{bmatrix} {- 1} & {- 2} & {- 1} \\ 0 & 0 & 0 \\ 1 & 2 & 1 \end{bmatrix}$ and ${E\_ v} = \begin{bmatrix} {- 1} & 0 & 1 \\ {- 2} & 0 & 2 \\ {- 1} & 0 & 1 \end{bmatrix}$

The edge metric value may be calculated as follows as the convolution of the edge detection weighting matrices with the 3×3 neighborhood NH9(x₀) of the target pixel:

EM(x ₀)=|NH9(x ₀)*E _(—) h|+|NH9(x ₀)*E _(—) v|

With the edge metric having been determined for each pixel in a pixel block, the pixel block may be classified as either an edge block or not an edge block, as indicated at 308. The classification of the block depends on the classifications of the pixels within the block as “edge pixels”, “non-edge pixels” or “texture pixels”. A pixel is classified as an edge pixel if its edge metric exceeds a threshold “edge_th”. In some embodiments, edge_th is set at 96. A pixel is classified as a non-edge pixel if its edge metric is less than a threshold “non_edge_th”. In some embodiments, non_edge_th is set at 32. A pixel is classified as texture pixel if it is neither an edge pixel nor a non-edge pixel. A pixel block is classified as an edge block if the number of edge pixels in the block exceeds a threshold “edge_block_th”. In some embodiments (for 8×8 blocks), edge_block_th is set at 4.

If a pixel block is not classified as an edge block at 308, then it is determined, as indicated at 310, whether the pixel block in question has a “strong edge block” as a neighbor. A block is classified as a strong edge block if it has at least one pixel for which the edge metric exceeds a threshold “strong_edge_th”. In some embodiments, strong_edge_th is set at 128.

FIG. 4 schematically illustrates an aspect of the determination as to whether a pixel block is neighbored by a strong edge block. The squares shown in FIG. 4 each represent pixel blocks. Pixel block 402, marked with an “X”, is the block for which the determination is currently being made as to whether it is neighbored by a strong edge block. In some embodiments, if any one of the pixel blocks 404, 406, 408, 410, 412, 414, 416, 418 is a strong edge block, then pixel block 402 is considered to be a neighbor of a strong edge block. In other embodiments, to reduce processing complexity and memory requirements, pixel blocks 414, 416, 418, all marked “Y′” and below the target block 402 in the image, are disregarded; in these embodiments, pixel block 402 is considered to be a neighbor of a strong edge block only if at least one of the blocks marked “Y” (i.e. blocks 404, 406, 408, 410 and 412) is a strong edge block.

If a particular block is determined to be either an edge block or a neighbor of a strong edge block, then, as indicated at 312 in FIG. 3, it is next determined whether the block in question is a “low activity” block. This determination is made because mosquito noise is most likely to be visible in a block with little visual activity that is either an edge block or the neighbor of a strong edge block. As indicated by logical connection 313 in FIG. 3, the classification of the blocks selected at 308 or 310 as low activity blocks or not low activity blocks may be performed on a version of the input video signal that has not been pre-filtered. In other words, the video input signal subjected to processing for identification of low activity blocks may by-pass the pre-filtering represented at 304.

A block is classified as a low activity block if two conditions are satisfied. The first condition is that the number of non-edge pixels in the block exceeds a threshold. In some embodiments the threshold is set at 32. The second condition is that the number of non-edge pixels in the block exceeds a product obtained by multiplying the number of texture pixels in the block by a threshold factor. In some embodiments the threshold factor is set to 1; in this case the second condition becomes simply that the number of non-edge pixels in the block exceed the number of texture pixels in the block.

In the previous paragraph, a procedure was described for determining whether a block is a low activity block based on edge characteristics of the pixels in the block. However, in other embodiments, the classification of a block as a low activity block may be made without utilizing edge characteristics. In this alternative, each pixel in the block is classified as a “low activity” pixel or not a low activity pixel based on the statistical variance of pixel values in the neighborhood of the pixel to be classified. To make this classification, a variance metric Var(x₀) is calculated for the target pixel (the pixel to be classified) according to the following formula:

${{Var}\left( x_{o} \right)} = {\left( {1/N} \right)*{\sum\limits_{x \in {{NH}\; {(x_{o})}}}\left( {\left\{ x \right\} - \left( {\left( {1/N} \right)*{\sum\limits_{x \in {{NH}{(x_{o})}}}\left\{ x \right\}}} \right)} \right)^{2}}}$

where:

-   -   NH(x₀) is the set of N pixels (N=9, for example) which forms the         neighborhood of the target pixel, and     -   {x} is the value of pixel x which is in the neighborhood of the         target pixel.

The target pixel is classified as a low activity pixel if its variance metric Var(x₀) is less than a threshold. In some embodiments the threshold may be set at 1024 (assuming a range of zero to about 14,600 for possible pixel values). The pixel block, in turn, may be classified as a low activity block if the number of low activity pixels in the block exceeds a threshold, which may be set at 32.

In some embodiments, the following simplified formula may be used to calculate Var(x₀), in order to reduce processing complexity:

$\left( {1/N} \right)*{\sum\limits_{x \in {{NH}\; {(x_{o})}}}{{\left\{ x \right\} - x_{o}}}}$

Once a block that is an edge block or neighbors a strong edge block has also been classified as a low activity block, the pixels in the block are examined pixel by pixel (as indicated at 314) to determine for each pixel whether it has a value that reflects a mosquito noise artifact. To determine whether a particular target pixel in such a block is a mosquito noise pixel, a motion metric is calculated for the target pixel. FIG. 5 schematically illustrates aspects of the calculation of the motion metric. As will be seen, the motion metric is calculated as the sum of absolute differences, where an “absolute difference” is the absolute value of a difference between the respective values of two pixels.

A group of pixels 502 illustrated in FIG. 5 includes the current target pixel 504 (shaded) and its four nearest neighbor pixels, which are pixel 506 (immediately above the target pixel), pixel 508 (immediately below the target pixel), pixel 510 (immediately to the left of the target pixel) and pixel 512 (immediately to the right of the target pixel). The group of pixels 522 illustrated in FIG. 5 are the pixels in the immediately preceding image that correspond in location to the pixels of group 502. In particular, the pixels of group 522 are pixel 524 (corresponding in position to target pixel 504), pixel 526 (corresponding in position to pixel 506), pixel 528 (corresponding in position to pixel 508), pixel 530 (corresponding in position to pixel 510), and pixel 532 (corresponding in position to pixel 512). The motion metric for target pixel 504 is calculated as the sum of the absolute differences between each pixel in group 502 and the corresponding pixel in group 504. In other words, the motion metric is calculated as the sum of the following absolute differences: (a) the absolute difference between pixels 504 and 524; (b) the absolute difference between pixels 506 and 526; (c) the absolute difference between pixels 508 and 528; (d) the absolute difference between pixels 510 and 530; and (e) the absolute difference between pixels 512 and 532.

If the motion metric for the target pixel exceeds a threshold, then the target pixel is classified as a “motion pixel”. In some embodiments this threshold is set at 20. If the target pixel is not a motion pixel, and its motion metric is less than another threshold, then the target pixel is classified as a “non-motion pixel”. In some embodiments, the latter threshold is set at 6. If the target pixel is neither a motion pixel nor a non-motion pixel (i.e., the target pixel is in a range defined by the two thresholds), it is classified as a “mosquito noise pixel”.

The pixels classified as mosquito noise pixels are reported as such by the mosquito noise detector 204 (FIG. 2) to the mosquito noise filtering block 206, as indicated at 316 in FIG. 3. The mosquito noise filtering block 206 may apply a filtering process (e.g., a low pass filter) at each mosquito noise pixel identified by the mosquito noise detector. For example, a median filter may be applied at each mosquito noise pixel, where the output of the filter is the median value of the pixels in a three-pixel-by-three-pixel area centered on the mosquito noise pixel.

It may be desirable to provide an overall mosquito metric for each image as an indication of the extent of mosquito noise artifacts in the image. This metric may be used, for example, to determine whether to apply mosquito noise reduction filtering or whether to apply other post-processing procedures to the image. For example, if the metric indicates that the image is highly degraded, it may be determined that mosquito noise reduction filtering should not be applied. In some embodiments, the metric may be calculated by summing the respective motion metric for each mosquito noise pixel in the image and then dividing the resulting sum by the total number of mosquito noise pixels in the image.

By identifying specific pixels that reflect mosquito noise artifacts, the above-described procedure makes it possible to target filtering to mitigate mosquito noise. Thus the negative effect of mosquito noise on image quality may be ameliorated without blurring the entire image. The procedure described above has relatively low computational complexity as compared to frequency domain analyses that may be proposed to address mosquito noise.

FIG. 6 is a functional block diagram that illustrates aspects of another noise reduction process that may be performed in the post-processing block in accordance with some embodiments. The noise reduction process of FIG. 6 may be performed in addition to, or instead of, the noise reduction process described above with reference to FIGS. 2-5. Block 602 represents the post-processing block (or a noise reduction sub-block) receiving an input video signal (e.g., directly or indirectly from the video decoder 104) that is to be subjected to noise reduction processing. Block 604 represents a process provided in accordance with some embodiments to detect locations (e.g., specific pixels), in the video signal received at 602, which exhibit ringing noise artifacts. Block 606 represents a process in which filtering is applied to the input video signal received at 602 (based on results obtained by the ringing noise detector 604), to mitigate the ringing noise artifacts.

FIG. 7 is a flow chart that illustrates a ringing noise detection process performed by the ringing noise detector sub-block of the pre-processing/noise reduction block 106 in accordance with some embodiments. Block 702 in FIG. 7 represents receipt by the ringing noise detector sub-block 604 of the decompressed video signal to be filtered for purposes of ringing noise reduction.

Like the mosquito noise detection process described above, the ringing noise detection process of FIG. 7 may be at least partly based on pixel blocks. 8×8, 10×10 or other block dimensions may be used.

Block 704 in FIG. 7 represents pre-filtering that may be applied to the input video signal before performing edge detection processing. The pre-filtering is not required but may improve the accuracy of the subsequent edge detection. The pre-filtering applied at 704 may be performed in the same manner as the pre-filtering described above in connection with block 304 in FIG. 3.

Edge detection processing as indicated at 706 follows the pre-filtering at 704. With the edge detection processing, the above-described edge metric value EM(x₀) is calculated for each pixel. Based on the edge metric values, blocks that are likely to exhibit ringing noise artifacts are identified. These blocks may be (a) edge blocks that include a smooth region and (b) blocks having a strong edge. Various type of edge detectors may be employed, including the Sobel edge detector as described above in connection with block 306 in FIG. 3.

With the edge metric having been determined for each pixel in a pixel block, it is next determined (as indicated at 708) whether the pixel block should be classified as an edge block which has a smooth region. The classification of the block depends on the classifications of the pixels within the block as “edge pixels”, “non-edge pixels” or “texture pixels”. The classification of pixels may be made in the same manner as described above in connection with block 308 in FIG. 3, except that in some embodiments the threshold “edge_th” may be set at 80 instead of 96. A pixel block may be considered to be an edge block if the number of edge pixels in the block exceeds a threshold. In some embodiments, for ringing noise detection purposes the latter threshold is set at zero; in other words, in these embodiments, a pixel block is considered to be an edge block if any of its pixels is an edge pixel.

If a pixel block is considered to be an edge block, it is next determined whether it has a smooth region. The pixel block is considered to have a smooth region if two conditions are satisfied. The first condition is that the number of non-edge pixels in the block exceeds a threshold. In some embodiments the threshold is set at 40. The second condition is that the number of non-edge pixels exceeds a product obtained by multiplying the number of texture pixels in the block by a threshold factor. In some embodiments the threshold factor is set to 1; in this case the second condition becomes simply that the number of non-edge pixels in the block exceeds the number of texture pixels in the block.

In the previous paragraph, a procedure was described for determining whether a block has a smooth region based on edge characteristics of the pixels of the block. However, in other embodiments, the determination of whether a block has a smooth region may be made without utilizing edge characteristics. In this alternative, each pixel in the block is classified as a “low activity” pixel or not a low activity pixel based on the statistical variance of pixel values in the neighborhood of the pixel to be classified. To make this classification, a variance metric Var(x₀) is calculated for the target pixel (the pixel to be classified) according to the following formula:

${{Var}\left( x_{o} \right)} = {\left( {1/N} \right)*{\sum\limits_{x \in {{NH}\; {(x_{o})}}}\left( {\left\{ x \right\} - \left( {\left( {1/N} \right)*{\sum\limits_{x \in {{NH}{(x_{o})}}}\left\{ x \right\}}} \right)} \right)^{2}}}$

where:

-   -   NH(x₀) is the set of N pixels (N=9, for example) which forms the         neighborhood of the target pixel, and     -   {x} is the value of pixel x which is in the neighborhood of the         target pixel.

The target pixel is classified as a low activity pixel if its variance metric Var(x₀) is less than a threshold. In some embodiments the threshold may be set at 1024. The pixel block, in turn, may be considered to have a smooth region if the number of low activity pixels in the block exceeds a threshold, which may be set at 20 for purposes of ringing noise detection.

In some embodiments, the following simplified formula may be used to calculate Var(x₀), in order to reduce processing complexity:

$\left( {1/N} \right)*{\sum\limits_{x \in {{NH}\; {(x_{o})}}}{{\left\{ x \right\} - x_{o}}}}$

If a pixel block is not classified at 708 as an edge block which has a smooth region, then it is determined, as indicated at 710, whether the pixel block in question is a “strong edge block”. A block is classified as a strong edge block for ringing noise detection purposes if it has at least one pixel for which the edge metric exceeds a threshold. In some embodiments, for ringing noise detection purposes the latter threshold is set to 112.

For each block that has been classified either as a strong edge block or as an edge block that has a smooth region, the pixels in the block are examined pixel by pixel (as indicated at 712) to determine for each pixel whether it has a value that reflects a ringing noise artifact. As indicated by logical connection 713 in FIG. 7, the determination as to whether pixels are ringing pixels may be performed on a version of the input video signal which by-passed pre-filtering.

To determine whether a particular target pixel in such a block is a ringing noise pixel, four local complexity metrics are calculated for the target pixel.

The first local complexity metric CM_(—)1h(x₀) is calculated as the sum of the absolute difference between the target pixel and the pixel immediately to the left of the target pixel and the absolute difference between the target pixel and the pixel immediately to the right of the target pixel.

The second local complexity metric CM_(—)1v(x₀) is calculated as the sum of the absolute difference between the target pixel and the pixel immediately above the target pixel and the absolute difference between the target pixel and the pixel immediately below the target pixel.

The third local complexity metric CM_(—)2h(x₀) is calculated as the absolute difference between the pixel immediately to the left of the target pixel and the pixel immediately to the right of the target pixel.

The fourth local complexity metric CM_(—)2v(x₀) is calculated as the absolute difference between the pixel immediately above the target pixel and the pixel immediately below the target pixel.

The target pixel is classified as a “ringing pixel” if either one of the following two conditions is met. The first condition is that the first local complexity metric CM_(—)1h(x₀) exceeds the product obtained by multiplying the third local complexity metric CM_(—)2h(x₀) by a threshold factor. The second condition is that the second local complexity metric CM_(—)1v(x₀) exceeds the product obtained by multiplying the fourth local complexity metric CM_(—)2v(x₀) by a threshold factor. In some embodiments the threshold factor is set at 2 in both cases.

The pixels classified as ringing pixels are reported as such by the ringing noise detector 604 (FIG. 6) to the ringing noise filtering block 606, as indicated at 714 in FIG. 7. The ringing noise filtering block 606 may apply a filtering process (e.g., a low pass filter) at each ringing noise pixel identified by the ringing noise detector. In some embodiments, the filtering at each ringing noise pixel may be the same type of median filter described above in regard to filtering at mosquito noise pixels.

It may be desirable to provide an overall ringing noise metric for each image as an indication of the extent of ringing noise artifacts in the image. This metric may be used, for example, to determine whether to apply ringing noise reduction filtering or whether to apply other post-processing procedures to the image. For example, if the metric indicates that the image is highly degraded, it may be determined that ringing noise reduction filtering should not be applied.

In some embodiments, the overall ringing noise metric for the image may be calculated by summing the respective variance metric Var(x₀) for each ringing pixel in the image and then dividing the resulting sum by the total number of ringing pixels in the image.

By identifying specific pixels that reflect ringing noise artifacts, the above described procedure makes it possible to target filtering to mitigate ringing noise. Thus the negative effect of ringing noise on image quality may be ameliorated without blurring the entire image.

The mosquito noise detector and/or ringing noise detector blocks, or other blocks herein, may be implemented as application-specific logic circuitry or by one or more programmable processors controlled by software instructions stored in a memory or memories coupled to the processor or processors.

The several embodiments described herein are solely for the purpose of illustration. The various features described herein need not all be used together, and any one or more of those features may be incorporated in a single embodiment. Therefore, persons skilled in the art will recognize from this description that other embodiments may be practiced with various modifications and alterations. 

1-9. (canceled)
 10. A method comprising: making a first determination as to whether a current pixel exhibits a ringing artifact; and determining whether to apply a filtering process at said current pixel based on a result of said first determination.
 11. The method of claim 10, wherein said first determination includes calculating four local complexity metrics at said current pixel.
 12. The method of claim 11, wherein: a first one of the complexity metrics is a sum of absolute differences between said current pixel and its nearest neighbors in an x-axis direction; a second one of the complexity metrics is a sum of absolute differences between said current pixel and its nearest neighbors in a y-axis direction; a third one of the complexity metrics is an absolute difference between nearest neighbors of said current pixel in said x-axis direction; and a fourth one of the complexity metrics is an absolute difference between nearest neighbors of said current pixel in said y-axis direction.
 13. The method of claim 12, wherein said first determination includes at least one of: comparing said first one of the complexity metrics with a product obtained by multiplying said third one of the complexity metrics with a first threshold factor; and comparing said second one of the complexity metrics with a product obtained by multiplying said fourth one of the complexity metrics with a second threshold factor.
 14. The method of claim 13, wherein the first threshold factor equals the second threshold factor.
 15. The method of claim 14, wherein both the first and second threshold factors are equal to
 2. 16. The method of claim 10, wherein said first determination is made only with respect to selected pixel blocks of an image.
 17. The method of claim 16, wherein the selected pixel blocks are selected based at least in part on respective edge metric scores of pixels included in the pixel blocks.
 18. A method comprising: identifying a plurality of pixels in an image as exhibiting mosquito noise artifacts; summing respective motion metrics at said identified pixels to produce a sum; and dividing said sum by a total number of said identified pixels.
 19. The method of claim 18, wherein, for each of said identified pixels, said respective motion metric was calculated by adding absolute differences between a group of pixels centered on said each of said identified pixels and corresponding pixels of a previous image in a sequence of images.
 20. The method of claim 18, wherein said identifying said plurality of pixels includes comparing motion metrics for said pixels with a threshold.
 21. A method comprising: identifying a plurality of pixels in an image as exhibiting ringing noise artifacts; summing respective variance metrics of said identified pixels to form a sum; and dividing said sum by a total number of said identified pixels.
 22. The method of claim 21, wherein said identifying includes calculating four local complexity metrics for each of said pixels.
 23. The method of claim 22, wherein said identifying includes comparing one of said local complexity metrics with a multiple of another of said local complexity metrics. 